Currently, there's no provision for remapping the keyboard shortcuts. Maybe later...

The following are currently mapped

• ctrl-alt s = Search
• ctrl-alt m = Home
• ctrl-alt r = Recent
• ctrl-alt b = Bookmarks
• ctrl-alt h = History
• ctrl-alt ? = Help (note that ? = shift-/)

Also, on certain pages, letters and arrows will allow you to navigate through the listed items. Enter will take you to the selected item. Currently set up are:

• All of the SiteList pages (Bookmarks, History, Recent, Draft, Recent Edits)
• Any list of site contents

On certain pages, keys are mapped to give you key-only control. Here's a list:

Editing:

• Alt-s - save via ajax (note this doesn't work for new items, only items that have been saved before)
• Alt-Shift-s - same as clicking the save button (works on new items).
• Alt-w - toggle "Writing Mode"

The site uses SSL. This secures your connection to the server, and data flowing over the Internet is as safe from interception and theft as anything using SSL. You may choose to add another layer of encryption, where your data is encrypted in the browser and sent to the server (and stored in the database) that way. In this case, the clear-text version of your information never exists anywhere except on your machine. Were the database hacked, or if someone stole the database machine and looked through it for your information, all they'd find would be encrypted data.

When encrypting on the client, you enter a pass phase, which never leaves your machine. It's stored in local storage in the browser so you don't have to reenter it each time, but it is cleared when your session ends--when you close the tab or your browser. As nobody ever sees your pass phrase, nobody can ever help you if you lose/forget it. You can employ as many pass phrases as you want (for different sites or pieces of data), but you'll have to keep track of all that yourself. Personally, it'd suggest using only one pass phrase for everything.

Sites, or parts of sites, may be encrypted. Encryption options are: none, mixed, and all. None and all trigger a process whereby all the items involved get pulled to the client from the server and encrypted/decrypted, then sent back and stored. This could take time and bandwidth for a large number of notes. Mixed allows you to encrypt or decrypt individual notes by checking the "Encrypted" checkbox and saving. 

To set the encryption option for an entire site, edit the Site Definition. This encryption setting is automatically inherited by everything in the site. To change encryption settings for individual containers (Topics), edit the Topic's encryption option and choose to pass this option on to children or not. In mixed mode, encrypt or decrypt individual notes using the Encrypted checkbox.

The Encryption Page will show you which of your sites have encrypted notes. 

Be aware that nobody can see encrypted material without the passphrase. Obviously, you would never want to encrypt a public site.

Also be aware that the encryption process roughly doubles the quantity of data, so more is sent over the wire, and loading is a little slower. The encryption/decryption occurs in your browser, so only you can judge the performance hit from the encryption/decryption routines.

Another point about client-side encryption: Search can't look through encrypted data.

WebNotes allows you to move items from place to place. Most of the time, this is very simple--specify what you want to move and where to. However, particularly when moving from one site to another, the move process can be slightly more complicated.

Let's say you have a simple blog site which contains Topics and Posts. The Topics can contain Posts, but not more Topics (only one level allowed). Now let's say you have a note site which can have multiple levels of Topics as well as Notes. You want to move from the notes site to the blog site. We can automatically map the Topics from one site to the other, and we can easily map the Notes to Posts. However, the blog site doesn't allow nested Topics. We fix this by flattening out the Topics--they all get added to the target location, and it is then up to you to finish sorting out where you want everything. Note that moving the other direction, from blog to notes is trivial.

Now let's say you have a notes site without nested Topics, but the Topics can contain Notes or Links. When copied to the blog site, the Topics are all fine, but we have no way to keep the Links. They will be automatically converted into the only leaf-type node allowed: Posts.

If moving the other way, from blog to notes with Notes and Links, we have no clear way to determine what you want, so we bring up an interactive screen which allows you to map your Posts to a selection of Notes and Links. (Obviously, you probably want them all as Notes, but there are plenty of situations where this is unclear, and in general, we try not to over guess your intent.)

Sites can be created for specific needs. From a simple blog to a complex hierarchy of notes, you define sites @Html.ActionLink("here.", "Create", "Sites")

The site name should be a single word use to uniquely identify the site. ("Unique" only refers to unique to you, not to everyone.) This name is used in the address bar, as well as internally, to refer to the site by name.

The site header is used for display purposes--the header will show in the bar at the top and is how the viewer sees the site.

Comments aren't supported yet.

Permission determines whether other users can see, edit, add to, or delete from your site.

The site type determines the structure of the site. Currently, the only valid choices are Blog and Notes. These are predefined site types that will let you get going and see how the system works.

A Blog site is a simple arrangement where you can add posts to a sequential list. You can also create "topics," which are effectively containers for posts.

A Notes site is a little more complicated in that you create top-level "categories" which can each contain "topics" and "notes." Topics can contain sub-topics, nested indefinitely.

This site is for storing and displaying informtaion.

Different types of information want different formats, so WebNotes allows you to define a format for your information.

The most basic format might require nothing more than a list of notes on a page; a more complex format might require categories and topics, sub-topics, possibly relationships between topics, and notes within.

A 'site' is a top-level collection which contains a variety of elements within.

Ownership is defined as the actual owner or any surrogate granted explicit ownership privledges.

The owner(s) of a site have complete control of everything within the site, regardless of permission settings.

Non-owners can have access granted explicitly, or via the public access setting.

New elements inherit access from their parents, though this access can subsequently be changed.

If you mark a site as public, you can make individual elements private--this gives you the flexibility to have holding or preview areas for a site.

Similarly, you can make an individual element within a private site public.

When you change the access on an element, the default is to have everything within it change to the same access. You can override this behavior by clearing the "include children" checkbox.

Care must be taken in organizing access. A user could have access to an element, but not have access to child elements. If that user can and chooses to delete that element, they effectively have indirect access to the children, in that the child elements will be also be deleted.

The following access levels are defined; each level implies the prior levels:

• None - no access granted
• Read - read access granted to the public or an explicitly indicated user
• Add - users may add new elements; the owner of the added element has complete control
• Write - non-owners may edit this element
• Change Access - non-owners may change the access setting on this element
• Delete - non-owners may delete elements that they don't own
• Ownership - non-owners have effective ownerwhip access. Expicit permission only, top-level sites only.

Contact.